docs(crawl): add ignoreRobotsTxt parameter to configuration reference#736
Closed
firecrawl-spring[bot] wants to merge 1 commit intomainfrom
Closed
docs(crawl): add ignoreRobotsTxt parameter to configuration reference#736firecrawl-spring[bot] wants to merge 1 commit intomainfrom
firecrawl-spring[bot] wants to merge 1 commit intomainfrom
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Co-Authored-By: micahstairs <micah@sideguide.dev>
firecrawl-spring
bot
force-pushed
the
docs/add-ignoreRobotsTxt-param
branch
from
87962f3 to
285632e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the
ignoreRobotsTxtparameter to the crawl configuration reference table infeatures/crawl.mdx. This parameter exists in the API but was undocumented, causing confusion for users trying to use it.The description notes that the feature requires account-level approval via support, matching the actual behavior.
Related Pylon Ticket
https://app.usepylon.com/issues?issueNumber=25960